Feature: add HTTP proxy support to webhook integrations#795
Feature: add HTTP proxy support to webhook integrations#795ozan-cristan wants to merge 1 commit intoCombodo:developfrom
Conversation
github-project-automation
bot
moved this to First review needed
in Combodo PRs dashboard
|
I only see a lot of new files added, no actual changes. Are you sure you committed towards the latest version of the |
|
You’re right to point that out. The reason you mostly see new files is because the directory So the changes are real, but they appear as new files because the target directory does not yet exist in develop. |
|
Well, that repository is located at https://github.com/Combodo/combodo-webhook-integration and not here in iTop base. |
|
@ozan-cristan Your proposition has been accepted functionally (this feature is interesting). Next step for us is technical review. |
|
Thank you for the feedback and for accepting the proposal.
I will create the pull request in the correct repository and close the
current one.
Best regards,Cristian Ozán
El mié, 11 mar 2026, 12:10 p. m., jf-cbd ***@***.***>
escribió:
… *jf-cbd* left a comment (Combodo/iTop#795)
<#795 (comment)>
@ozan-cristan <https://github.com/ozan-cristan> Your proposition has been
accepted functionally (this feature is interesting). Next step for us is
technical review.
As @Hipska <https://github.com/Hipska> said, could you please create your
pull request on the right repository, and close this one ?
Thank you
—
Reply to this email directly, view it on GitHub
<#795 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ARXY72W4ADOSFE2LW6OYC734QF6VFAVCNFSM6AAAAACRTLODLKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAMZZHEYDIMJYGU>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
4 participants
Base information
Symptom (bug) / Objective (enhancement)
In many enterprise environments, iTop servers do not have direct access to the Internet and must route all outbound HTTP/HTTPS traffic through a corporate proxy.
Currently, the webhook integration module does not provide any way to configure a proxy for outbound requests.
As a result, webhook calls fail in restricted networks, usually with DNS resolution or connection errors, making integrations with external services (Telegram, Slack, APIs, etc.) unusable.
The objective of this enhancement is to allow webhook HTTP requests to be routed through a configurable proxy, making the webhook integration usable in secured and restricted infrastructures.
Reproduction procedure (bug)
(Not applicable, this is an enhancement and not a bug.)
Cause (bug)
(Not applicable, this is an enhancement and not a bug.)
Proposed solution (bug and enhancement)
The solution adds optional HTTP proxy support to the webhook request sender:
The proxy configuration is read from the module settings:
host(mandatory)user(optional)password(optional)When a proxy is defined, the corresponding CURL options are injected into the request:
CURLOPT_PROXYCURLOPT_PROXYTYPECURLOPT_PROXYUSERPWD(if authentication is configured)When no proxy is defined, the behavior remains unchanged, ensuring full backward compatibility.
This allows webhook integrations to work transparently in environments where Internet access is only available through a proxy.
The change is limited to the webhook integration module and does not impact any other part of iTop.